fix(deps): update all dependencies - #341

v26.10.1

Compare Source

Highlights

This release fixes a security issue in Black's bundled GitHub Action. Repositories that
use the action are encouraged to update to the latest version of Black immediately. This
update is received automatically when using psf/black@stable, and is independent of
the version of Black installed by the action.

When the GitHub Action reads version specifiers from tool.black.required-version, it
now only accepts released versions of Black, as it already did for black requirements
in dependency lists. Other values, such as URL references, are now rejected. This issue
has been registered as GHSA-cg8m-r9f2-5wm2; a CVE identifier is pending.

Stable style

• Fix a long Jupyter notebook assignment magic (for example x = !ls -la) being wrapped
  in parentheses, which IPython can no longer run; such cells are now left unchanged
  (#​5481)
• Keep repeated lines outside the selected --line-ranges unchanged (#​5436)
• Fix --line-ranges formatting lines that follow a statement when formatting joins or
  re-indents that statement (#​5484)
• Fix --line-ranges crashing with an internal error when an unselected statement has a
  # fmt: skip comment on the last line before a closing bracket (#​5477)
• Prevent moving an encoding declaration (for example # -*- coding: latin-1 -*-) onto
  the first two lines of a file (#​5487)
• Fix adding an extra trailing blank line inside a multi-line module docstring when its
  last line is near the line length limit (#​5494)
• Keep the parentheses around a walrus that is the only item in a set (for example
  {(x := f())}) when targeting Python 3.9 or older, since Python 3.8 and 3.9.0 can't
  parse it without them (#​5502)

Preview style

• Do not split short expressions on delimiters (such as binary operators, comparisons,
  or comprehensions) inside brackets when preceded by a standalone comment (#​5455)
• Fix the unstable string_processing feature removing backslash-newline sequences from
  raw strings, which changed their value (#​5482)
• Avoid adding unnecessary parentheses around unbreakable right-hand side expressions in
  assignments (such as annotated assignments or subscript targets) (#​5473)
• Parenthesize expressions with parameter comments when they exceed the line length
  under --preview (#​5442)
• Fix wrap_long_dict_values_in_parens dropping the parentheses around a right-hand
  side that contains a dictionary, leaving a line over the length limit (#​5492)
• Fix the unstable string_processing feature adding a space after * or ** in a PEP
  695 type parameter (* Ts = ...) when it splits a string in the parameter's default
  (#​5504)
• Avoid unnecessary line splits of trailers (such as indexing/subscripts) when an
  earlier bracket split exceeds the line length only due to a trailing comment (#​5498)

Configuration

• Add --cache-dir to configure the cache directory from the command line (#​5433)
• Don't cache a file as formatted after formatting or checking it with --line-ranges,
  which made a later full black --check pass and black skip the unformatted lines
  (#​5476)
• Respect a .gitignore that starts with a UTF-8 byte order mark. The mark became part
  of the first pattern, so that pattern never matched and Black formatted files that git
  ignores (#​5497)

Performance

• Avoid quadratic runtime when splitting very long lines with many trailing bracket
  pairs (such as consecutive subscripts) (#​5475)

Integrations

• Fix the GitHub Action crashing on dependency-group includes when use_pyproject is
  enabled (#​5479)
• When the GitHub Action reads version specifiers from tool.black.required-version, it
  now only accepts released versions of Black, as it already did for black
  requirements in dependency lists. Other values, such as URL references, are now
  rejected. (#​5510)

v26.10.0

Compare Source

Stable style

• --line-ranges no longer inserts an empty line after a docstring when the range
  covers only the docstring itself (#​5312)
• Fix # fmt: skip on a bracketed ternary turning the surrounding tuple into a call
  (#​5464)
• Fix crash when # fmt: skip is placed on a one-line function or class with PEP 695
  type parameters (#​5429)
• Fix an inline comment after the closing bracket of optional parentheses being moved
  inside the parentheses when the parenthesized expression contains own-line comments
  (#​5395)
• Fix unparseable output when # fmt: skip is placed on a bracket of an if, while,
  for, or with header (#​5401, #​5405)
• Fix crash when formatting parenthesized expressions with multiple inline comments and
  # fmt: skip (#​5414)
• Fix parsing Jupyter notebook assignment magics when non-ASCII characters appear
  earlier on the line (#​5381)
• Preserve blank lines that come immediately before a # fmt: on comment (#​5300)
• Keep the parentheses around the target of an annotated assignment (e.g.
  (x): int = 5), which prevent CPython from including the name in __annotations__
  (#​5321)
• Stop treating a t-string in docstring position as a docstring (e.g. t" spam " as
  the first statement of a module, class or function) (#​5287)
• Fix unparseable output for a t-string whose replacement field contains a quote (e.g.
  t'\'{a["b"]}\'') (#​5265)
• Fix unparseable output for a triple-quoted string whose body ends in an
  already-escaped double quote (e.g. '''\'''\"''') (#​5262)
• Fix --skip-magic-trailing-comma dropping the trailing comma from a split
  single-element tuple used as a lambda parameter default (#​5246)
• Fix unstable formatting when an inline comment sits on optional parentheses (e.g. a
  parenthesized assert message) (#​5241)
• Fix --skip-magic-trailing-comma dropping the trailing comma of a one-element
  subscript (a[x,]) when the line is long enough to be split and contains a power
  operator (#​5272)
• Fix crash when a standalone comment sits between tokens of a comprehension or lambda
  (#​5144)
• Fix inline comments on a bracket inside a comprehension being dropped (#​5330)
• Respect the magic trailing comma in a PEP 695 type parameter list containing a
  *TypeVarTuple or **ParamSpec (#​5244)
• Fix crash when a comment-only # fmt: off/# fmt: on block is followed by a with
  statement after another standalone comment (#​5189)
• Fix a crash when splitting case case if ... match patterns at very small line
  lengths (#​5147)
• Fix multiline docstring indentation when leading tabs are used inside indented
  docstrings (#​5148)
• Respect # fmt: skip on a line that opens a bracket (e.g.
  from x import ( # fmt: skip) when a standalone comment is among the bracket's
  contents (#​5161)
• Fix an AST safety error when separate # type: ignore comments in a parenthesized
  attribute chain were merged onto one physical line (#​5297)
• Preserve comments and blank lines outside requested ranges when formatting with
  --line-ranges (#​5175)
• Fix crash when # fmt: skip is used on one-line async def, async with, and
  async for statements containing a semicolon (#​5311)
• Stop converting form feeds or other similar characters in docstrings into newlines
  (#​5461)
• Fix --skip-source-first-line turning the skipped line's CRLF ending into \r\r\n
  when reformatting a file with CRLF line endings (#​5438)

Preview style

New preview features

• Add missing blank lines after classes whose last method has an ellipsis body (#​5439)
• Split only the brackets holding a magic trailing comma when more trailers follow them
  (e.g. stop splitting inside the [2] of [1,][2](3)) (#​5448)
• Keep dictionary keys containing operators together on one line when the value can be
  wrapped onto a new line instead (#​5435)
• Remove redundant parentheses around individual variables in unpacking targets (e.g.
  for (x), (y) in points: becomes for x, y in points:) (#​5416)
• Normalize uppercase T prefixes on t-strings to lowercase (#​5425)
• Remove redundant parentheses around generator expressions (#​5304, #​5369)
• Preserve two blank lines before a top-level class starting inside a # fmt: off block
  after an import (#​5238)
• Fix unnecessary parentheses around short right-hand expressions in indexed assignments
  (e.g. x[key] = expr) (#​5095)
• Parenthesize tuple expressions in yield statements for consistency with function
  calls and returns (#​5170)
• Stop splitting between a variable and its operator (not in, ==, is, ...) when
  the right-hand side is a bracketed expression, and instead split inside the brackets
  (#​5135)
• In .pyi stub files, enforce a blank line after a function or method that has a
  docstring-only body when another comment or statement follows it (#​5158)

Updates to existing preview features

• Fix crash in stub files when # fmt: skip is placed on a function in a group of
  same-name decorated functions (e.g. @overloads or a property setter) (#​5430)
• Keep the parentheses around a lambda used as the iterable of a comprehension (e.g.
  [x for x in (lambda: 0) if x]) (#​5176, #​5200)

Updates to existing unstable features

• Do not treat multi-line expressions with merged strings and trailing # type: ignore
  comments as single-line unsplittable expressions (#​5466)
• Fix duplicated inline comment when stripping the parentheses around a string or
  merging a backslash-continued string on the same line (#​5449)
• Split long stringified return annotations even when the function has parameters
  (#​5427)
• Don't hug brackets when doing so would join two # type: ignore comments onto one
  line (#​5271)
• Fix a crash when # type: ignore is lost during formatting of a long parenthesized
  string (#​5329)
• Fix only the first part of an implicitly concatenated unmergeable string (e.g.
  r"..." r"...") being wrapped in parentheses (#​5434)

Configuration

• Add support for NO_COLOR environment variable to disable ANSI output (#​5129)
• Remove spurious target version warning when runtime version is included in a
  --target-version flag (#​5167)
• Fix --force-exclude not excluding files whose path contains .. (e.g.
  black ../generated/file.py run from a subdirectory) (#​5471)
• Fall back to the default configuration, with a warning, when the given sources share
  no common project root (e.g. they are on different drives on Windows) instead of
  crashing (#​5386)
• Fix loading a stale cached pyproject.toml path when --code is used from different
  working directories in the same process (#​5152)
• Add validation for --line-ranges values (#​5107)
• Ignore empty cache files instead of raising an EOFError (#​5192)
• Reject non-string include and force-exclude values in pyproject.toml (#​5193)
• Validate BLACK_NUM_WORKERS values and report invalid values as usage errors instead
  of crashing (#​5211)
• Ignore permission errors when reading cache (#​5258)

Packaging

• Reduce the size of Linux standalone binaries by stripping debug symbols during the
  PyInstaller release build (#​5223)
• Black is now released using GitHub
  Immutable Releases
  (#​5296)

Performance

• Fix superlinear runtime growth with the number of input files (#​5450)
• Improve performance on strings containing many consecutive backslashes (#​5163)
• Improve performance on files with many # fmt: skip/# fmt: off/# fmt: on comments
  (#​5169, #​5190, #​5232)
• Improve performance on long calls and collections (#​5177)
• Improve performance on multiline strings inside large collections (e.g. a dict literal
  with triple-quoted strings as values) (#​5188)
• Improve performance on files with many soft keywords (e.g. match/case blocks)
  (#​5186)
• Improve performance on long semicolon-separated statements (in the stable style) and
  large dict literals (in --preview) (#​5184)
• Improve performance of --line-ranges on files with many sibling blocks (a long
  if/elif chain, a match with many cases, or many top-level definitions) (#​5213)
• Improve performance on deeply nested bracketed expressions (#​5171, #​5242)
• Improve performance on lists and subscripts holding one long expression without
  operators (e.g. a long run of implicitly concatenated strings inside []) (#​5239)
• Improve performance on deeply chained operations (e.g. a long a ** b ** c ** ...
  chain) (#​5235)
• Improve performance on long if/elif chains and other compound statements with many
  clauses (#​5322)
• Improve performance of string_processing:
  • when merging implicitly concatenated f-strings containing long string literals
    (#​5165)
  • when merging long implicitly concatenated strings (#​5173, #​5194)
  • when rewriting large nodes (e.g. "%s ..." % (a, b, c, ...)) (#​5178, #​5199, #​5220)
  • when splitting long string literals (#​5183)

Output

• Report parser failures using editor-friendly path:line:column locations (#​5237)
• Fix crash when writing formatted code or diffs to a sys.stdout that has no buffer
  attribute (e.g. in Jupyter notebooks) (#​5411)
• Report parse failures on Black's own output as internal errors (#​5383)

Blackd

• Return HTTP 400 instead of 500 when the X-Python-Variant header is empty or has an
  empty entry (e.g. a trailing comma) (#​5428)
• Allow optional whitespace around comma-separated versions and pyi in the
  X-Python-Variant header (#​5441)

Integrations

• Remove unused migrate-black script (#​5319)
• Support PEP 440 version specifiers in tool.black.required-version for the GitHub
  Action (#​5399)
• Add outputs (is_formatted, change_count, same_count, failure_count) to GitHub
  Action runs (#​5408)

Documentation

• Document vim-python-pep8-indent, which provides an indentexpr for Black-style
  insert-mode indentation (#​5288)

v26.13.0: 26.13.0

Compare Source

Node.js 26.13.0

v26.12.1: 26.12.1

Compare Source

Node.js 26.12.1

v26.12.0: 26.12.0

Compare Source

Node.js 26.12.0

v26.11.1: 26.11.1

Compare Source

Node.js 26.11.1

v26.11.0: 26.11.0

Compare Source

Node.js 26.11.0

v26.10.0: 26.10.0

Compare Source

Node.js 26.10.0

v26.9.0: 26.9.0

Compare Source

Node.js 26.9.0

v26.8.2: 26.8.2

Compare Source

Node.js 26.8.2

v26.8.1: 26.8.1

Compare Source

Node.js 26.8.1

v26.8.0: 26.8.0

Compare Source

Node.js 26.8.0

v26.7.0: 26.7.0

Compare Source

Node.js 26.7.0

v26.6.0: 26.6.0

Compare Source

Node.js 26.6.0

v26.5.1: 26.5.1

Compare Source

Node.js 26.5.1

v26.5.0: 26.5.0

Compare Source

Node.js 26.5.0

v26.4.0: 26.4.0

Compare Source

Node.js 26.4.0

v26.3.1: 26.3.1

Compare Source

Node.js 26.3.1

v26.3.0: 26.3.0

Compare Source

Node.js 26.3.0

v26.2.0: 26.2.0

Compare Source

Node.js 26.2.0

v26.1.0: 26.1.0

Compare Source

Node.js 26.1.0

v26.0.0: 26.0.0

Compare Source

Node.js 26.0.0

v4.1.3

Compare Source

What's new in Pylint 4.1.3?

Release date: 2026-10-11

False Positives Fixed

• Fixed a false positive for attribute-defined-outside-init when an
  attribute is assigned inside the setter of an old-style, non-decorator
  property(fget, fset) call. The decorator form (@property /
  @x.setter) was already exempted by the fix for #​409; the classic
  call form was not.

  Closes #​3325

• Fix a false positive for used-before-assignment when a name bound by an earlier
  target of the same assignment is used by a later target, as in a = b[a] = 0.

  Closes #​5955

• Fix a no-member false positive in a comprehension inside a branch that
  cannot run, such as if sys.platform == "win32": on Linux. Like the rest of
  the branch, the comprehension is no longer checked for missing members.

  Closes #​7240

• Fix a false positive for used-before-assignment when a name bound by a tuple
  or list target of a with item is used by a later item of the same with statement.

  Closes #​7545

• Fix false positives such as not-callable, not-an-iterable,
  unpacking-non-sequence and no-member on the result of a function whose
  body is only ..., like @overload and .pyi stubs. Such calls were
  inferred as returning None. This affected sqlalchemy.func,
  pydantic.Field, and the torch functions wrapped by _add_docstr,
  such as torch.linalg.qr.

  Closes #​8138
  Closes #​9218
  Closes #​9354
  Closes #​10087

• Fix a false positive for protected-access when a subclass of a subscripted
  generic base, such as class Child(Parent[T]), accesses a protected member
  through that base, such as Parent._foo(self).

  Closes #​8600

• Avoid emitting unreachable for a yield immediately after raise or
  sys.exit() that marks a function as a generator, matching the existing
  handling of return.

  Closes #​8909

• Fix a false positive for super-init-not-called in .pyi stub files, where
  every __init__ body is ... and cannot call the parent's __init__.

  Closes #​9096

• Fix a false positive for possibly-used-before-assignment when a lambda
  uses its parameters, including from a nested lambda, and that name is assigned
  later in the module.

  Closes #​9126

• Fix a false positive for useless-parent-delegation when a keyword-only
  parameter is passed to the parent under the same keyword but with a different value.

  Closes #​9226

• Fix a false positive for unused-argument in .pyi stub files, where
  function bodies are ... and cannot use their arguments.

  Closes #​9417

• Fix a false positive for used-before-assignment when a name assigned with an
  assignment expression in the condition of a comprehension is used in its element,
  for example [y for x in data if (y := f(x))].

  Closes #​9460

• Fixed false positive arguments-differ and signature-differs for
  typing.overload stubs. Overload stubs in a subclass are no longer compared
  to the overridden method, and an overridden method with overloads is compared
  through its implementation instead of its first stub.

  Closes #​10186
  Closes #​5264

• Stop emitting redefined-variable-type when the bare _ variable is
  reused to discard values of different types.

  Closes #​10374

• Allow the __main__ module name in the camelCase, PascalCase and
  UPPER_CASE naming styles without reporting invalid-name.

  Closes #​10442

• Fixed a false positive for unexpected-keyword-arg when a decorator that
  returns its argument unchanged is stacked above a decorator accepting **kwargs.

  Closes #​10831

• Fix invalid-name false positives for module-level all-caps aliases that
  preserve the name of an external callable.

  Closes #​11012

• redefined-builtin no longer warns for method parameters that retain a
  built-in name from an overridden method.

  Closes #​11438

• Fixed a false positive for useless-suppression of line-too-long when a # inside a string literal comes before the # pylint: disable=line-too-long comment.

  Closes #​11440

• Fix a false positive for unnecessary-ellipsis when an ellipsis is the
  sole body statement of a Protocol method defined inside a conditional block
  such as if TYPE_CHECKING:.

  Closes #​11459

• Fix a false positive for unnecessary-negation when negating a comparison
  between instances of a set or frozenset subclass.

  Refs #​11513

Other Bug Fixes

• Fix pyreverse hanging or crashing with a RecursionError when
  --all-associated (-S) follows an attribute whose inferred class is rebuilt by
  astroid on every inference, such as a numpy array.

  Closes #​3602

• Fix a crash in pyreverse when a diagram includes a class created by
  namedtuple, or an argparse.Namespace.

  Closes #​10767

• The "difference" column of the "Messages by category" and "Duplication" reports
  (--reports=y) now shows the change since the previous run instead of repeating
  the previous count.

  Closes #​11520

• Fixed nested-min-max suggesting a non-equivalent rewrite when an inner
  min/max call had multiple arguments.

  Refs #​11593

• Using several output formats that all write to stdout (for example --output-format=colorized,no-header)
  now raises an error instead of printing every message more than once.

  Closes #​11597

• Fixed an IndexError crash in the typecheck checker when an Enum class defines an __init__ method without arguments.

  Closes #​11608

• Fix a crash in the duplicate-code checker when min-similarity-lines is set to 0.
  The checker is now disabled in that case, as documented.

  Closes #​11625

v4.1.2

Compare Source

What's new in Pylint 4.1.2?

Release date: 2026-10-03

False Positives Fixed

• Fixed a false positive unbalanced-tuple-unpacking when unpacking a tuple
  concatenation whose elements have several possible values.

  Fixed by upgrading astroid to 4.3.3.

  Closes #​2621

Other Bug Fixes

• Fixed a crash when calling __bases__ on a class.

  Fixed by upgrading astroid to 4.3.3.

  Closes #​11491

• Fix a crash (astroid-error) when the class of a called attribute cannot
  be fully inferred, for example when the attribute is used as a with
  statement target or inside a comprehension.

  Closes #​11492

• Fix a crash when a name bound by a type statement (a TypeVar) is used in a with statement.

  Closes #​11510

• Fixed a crash (TypeError) in the variables checker when checking a class
  whose metaclass name binding has no line number, for example a class defined
  with metaclass=__annotations__.

  Closes #​11511

• Fix a crash in the using-final-decorator-in-unsupported-version check
  when import final is used.

  Closes #​11521

• Fix a crash when a plugin passes confidence=None to add_message, as
  pylint-pytest does, for a message that is disabled. confidence=None is
  accepted again and means UNDEFINED, like in pylint 4.0. Passing it
  explicitly to add_message, add_ignored_message or Message now emits a
  DeprecationWarning: it will raise an error in pylint 5.0.

  Closes #​11530

v4.1.1

Compare Source

What's new in Pylint 4.1.1?

Release date: 2026-09-29

Other Changes

• Pylint 4.1.0 could not be uploaded to PyPI, because it required an unreleased
  version of dill on Python 3.15, and PyPI refuses such a dependency. 4.1.1 is
  the first 4.1 release available on PyPI, see the 4.1.0 changes below.

  Refs #​11495

v9.2.0

Compare Source

pytest 9.2.0 (2026-10-27)

Removals and backward incompatible breaking changes

• #​14716: -c now raises a usage error for a path that does not exist, is a directory, or is in a format pytest has no loader for. Such paths were previously either ignored or reported as an unhandled FileNotFoundError.

• #​8593: The indirect, ids and scope arguments of Metafunc.parametrize() <pytest.Metafunc.parametrize> -- and therefore of @pytest.mark.parametrize <pytest.mark.parametrize ref> -- are now keyword-only.

  Passing them positionally was a common source of confusing errors, e.g. parametrize("arg1", "arg2", [(1, 2)]) made the argvalues land in indirect and failed with indirect fixture '(1, 2)' doesn't exist; such mistakes now fail with an understandable TypeError. The type annotations have always declared these arguments as keyword-only.

• #​993: Plugin import failures at startup are now reported and classified instead of escaping as a raw traceback with the accidental exit code 1:

  • a plugin that cannot be found -- via -p, pytest_plugins or PYTEST_PLUGINS -- exits with pytest.ExitCode USAGE_ERROR (4), like a conftest.py that fails to import;
  • a plugin that is found but raises while importing -- including a broken pytest11 entry point or a missing plugin dependency -- exits with pytest.ExitCode INTERNAL_ERROR (3), with the traceback preserved.

  pytest.main now returns these codes instead of raising ImportError. Also fixed an IndexError from pytest's own internals when the plugin raised an exception with no arguments.

Deprecations (removal in next major release)

• #​14742: The private _pytest.python.CallSpec2 name has been renamed to CallSpec.
  The old CallSpec2 alias remains available for now and will be removed in pytest 10 or 11.

• #​14755: Schedule yield_fixture decorator for removal in pytest 10 or 11.

• #​14774: Similarly to the deprecation of class-scoped fixtures defined as instance methods in pytest 9.1,
  all higher-scoped fixtures (module, package, and session) defined
  as instance methods are now deprecated.

  They suffer from the same issue the original deprecation only fixed for
  class-scoped fixtures, see 10819 and 14011.

• #​14808: Passing a non-string value to a string-typed ini option now emits a pytest.PytestRemovedIn10Warning. This affects [tool.pytest.ini_options] in pyproject.toml. In pytest 10 this will raise a TypeError, matching the behavior of the corresponding TOML config path.

• #​7323: Passing bytes to TerminalReporter.write_line() is now deprecated, pass a str instead.

New features

• #​14743: Full diff: now contains a legend explaining the + & - symbols in diff output.
• #​2781: When strict_markers is enabled, marker names used in -m expressions are now validated against registered markers.
• #​6881: Added the parametrize_long_str_id_strategy configuration option to control how long str/bytes parameter values are handled in auto-generated test IDs. Explicit IDs set via ids=[...] or pytest.param(..., id=...) are not affected. Available strategies: short (default, values over 100 chars fall back to argname+index), sha256 (SHA-256 hex digest), legacy (keep full value), and disallow (error requesting explicit IDs).

Improvements in existing functionality

• #​10745: A RecursionError whose recursion origin cannot be located now shows only the
  first and last 10 stack frames, matching what pytest already did when locating
  the origin failed outright. Previously the full traceback -- often around a
  thousand near-identical frames -- was rendered, which was both slow and
  unreadable. Pass --full-trace to see every frame.

• #​10745: The line numbers of a module's statements are now computed once per traceback
  instead of once per traceback entry, which noticeably speeds up rendering
  failures raised from large test modules.

• #​11418: The cached rewritten modules in __pycache__ are now invalidated by a hash of
  the source instead of its modification time, using the checked-hash pyc format
  from 552.

  Timestamps make the cache useless wherever source files get fresh modification
  times, most notably in CI: a checkout gives every file a new mtime, so a
  restored cache is discarded in full and every test module is rewritten again.
  Hashing the source costs roughly 15 microseconds per file and makes the cache
  survive that.

  Existing timestamp based caches are ignored and rewritten once.

• #​12624: The pytest_plugins variable and the PYTEST_PLUGINS environment variable now also accept entry point names of installed plugins (e.g. xdist), in addition to importable module names, matching the behavior of the -p command-line option.

  As part of this change, plugins specified by entry point name through these mechanisms are now also listed in the plugins: line of the terminal header (12615).

  Based on the original implementation by Marcel Telka in 12616.

• #​12697: Warnings emitted while importing plugins through -p, PYTEST_PLUGINS, or entry point autoloading are now captured, filtered, and reported like other warnings.

• #​12860: Assertion diffs for dict.items() and dict.keys() comparisons (>=, <=, >, <, ==) now show which items are missing, the same way set comparisons do.

• #​13354: Node.get_closest_marker <_pytest.nodes.Node.get_closest_marker> now also accepts a ~pytest.MarkDecorator as its default, for example item.get_closest_marker("foo", pytest.mark.foo(1)), and returns the wrapped ~pytest.Mark.

  Previously the only way to build a default was to instantiate ~pytest.Mark directly, which is private and warns.

• #​13369: Improved the error from pytest.RunResult.assert_outcomes when a plugin changes or removes pytest's standard terminal summary, and documented how to isolate output-changing plugins.

• #​13431: Exposed pytest.ParameterSet as the type of the return value of pytest.param().
  This can be used in type annotations and isinstance checks.

• #​13564: Issue a warning when fixtures are wrapped with a decorator that prevents
  correct discovery, including @classmethod above @pytest.fixture and
  @staticmethod above @pytest.fixture. Put @pytest.fixture above
  those decorators on test classes.

• #​14164: Exposed pytest.Approx as the type of the return value of pytest.approx().
  This can be used in type annotations and isinstance checks.

• #​14463: Assertion diffs for mappings now match up keys the way the compared mappings match them themselves.

  Key comparison goes through the mappings' key views instead of plain sets of their keys, so a mapping
  with its own notion of key equivalence, such as case-insensitive header mappings, no longer
  reports its common keys as missing on either side.

• #​14523: Large assertion comparison diffs are now built lazily and capped to the
  truncation budget, so a huge diff is no longer formatted in full just to
  be truncated. As a consequence, the truncation footer no longer
  reports the exact number of hidden lines.

• #​14687: The default fd-level output capturing (--capture=fd) now skips reading the capture buffer for tests which produce no output, reducing per-test overhead in large test suites.

• #​14724: --no-summary now only applies directly to pytest's own summary.

  The flag no longer skips the pytest_terminal_summary hook, so third-party
  plugins (for example coverage) can still write their terminal summaries.

• #​14751: parser.addini <pytest.Parser.addini> now also accepts type expressions for its type argument, in addition to the existing string tags: the plain Python types str, bool, int, float, a Literal of strings, and unions of these (for example int | str or int | Literal["auto"]).

• #​14754: pytest.approx() now rejects infinite relative tolerances for datetime.timedelta values with a clear ValueError instead of raising OverflowError.

• #​14791: The junit_family, junit_logging, junit_duration_report, console_output_style, empty_parameter_set_mark, assertion_text_diff_style and tmp_path_retention_policy configuration options are now registered with the set of values they accept: an invalid value now fails with a clean usage error instead of being silently ignored or crashing later, and pytest --help lists the accepted values.

  config.getini <pytest.Config.getini> now raises pytest.UsageError instead of TypeError or ValueError when the value read from the configuration file does not match the registered type, so a bad value is always reported as a short usage error message instead of an internal error traceback. Asking for an option name that was never registered still raises ValueError.

• #​15006: pytest.approx now emits pytest.PytestApproxDecimalToleranceWarning when a rel or abs tolerance is given as a float that cannot be represented exactly for a ~decimal.Decimal comparison, since such a tolerance is widened to the float's exact binary value.

• #​14675, #​14953, #​15153, #​15132: The truncation_limit_lines, truncation_limit_chars, max_warnings, verbosity_assertions, verbosity_test_cases, verbosity_subtests, tmp_path_retention_count, log_level, log_cli_level, log_file_level,log_auto_indent and faulthandler_timeout configuration options now accept native integer (and, for log_auto_indent, boolean) values in TOML configuration files, while still accepting strings for backward compatibility.
  log_file_mode now reports invalid values as a usage error.

• #​15254: tmp_path and TempPathFactory.mktemp <pytest.TempPathFactory.mktemp> no longer list the whole base temporary directory on every call, which made sessions with many temporary directories quadratically slow. Numbers are now handed out from a per-prefix counter, skipping names that already exist.

• #​4569: Node.add_marker <_pytest.nodes.Node.add_marker> now stores a ~pytest.Mark in node.keywords, matching what marks applied during collection store. Previously it stored a ~pytest.MarkDecorator.

• #​9436: Avoided formatting tracebacks for tests marked with xfail(run=False).

Bug fixes

• #​10128: Configured warning filters now apply to warnings emitted by pytest_configure hooks.

• #​10210: pytest.approx now raises a TypeError for any nested container, not
  only for one of the same type as its parent. Previously approx([{"k": 1}])
  and approx({"k": [1]}) were accepted and then compared unequal to every
  value, silently ignoring the tolerance, while approx([[1]]) correctly
  reported that nesting is unsupported.

• #​10644: monkeypatch.setattr() no longer leaves a new entry in the instance __dict__ when it patches an attribute that the instance inherits from its class.

  Previously undo() assigned the inherited value onto the instance, which shadowed the class attribute -- permanently freezing the result for descriptors that resolve dynamically.

• #​1139: Fixed tracebacks showing ??? instead of source lines for code compiled with a filename relative to a directory other than the current working directory -- e.g. compiled Cython modules, when running pytest from a subdirectory of the project root.
  The source lookup now falls back to searching sys.path for such filenames, as the standard traceback module does.

• #​11502: The rootdir is no longer derived from a configuration file that is not a regular file, such as --config-file=/dev/null.

• #​11783: Plugins installed in editable mode (660) are marked for assertion rewriting again.

  Such installs do not record the package's Python files in the distribution metadata, so pytest found nothing to rewrite and assertions inside the plugin lost their introspection. The plugin's entry point is now used to locate the package in that case.

• #​11933: pytest.warns no longer re-emits unmatched warnings with module="warnings", which caused module-based warning filters to be applied to the wrong warnings. Since warnings.WarningMessage does not record the module a warning was emitted with, re-emitted warnings now use the standard warnings.warn_explicit default of deriving the module from the warning's filename.

• #​12175: ExceptionInfo.exconly(tryshort=True) <pytest.ExceptionInfo.exconly> now strips the AssertionError: prefix of failed assert statements for ~pytest.ExceptionInfo objects created by pytest.raises, and failures inside unittest.TestCase.subTest report the same short crash line as regular tests.

• #​12223: The message attribute of <failure> and <error> elements in --junitxml reports is now shortened to whole lines within 500 characters. When something is dropped, it ends with a note pointing to the element text, which still holds the full report. Previously, very verbose assertion output (e.g. with -vv) produced attributes tens of thousands of characters long, which some XML parsers fail on.

• #​12307: Fixed truncation of long collections (lists, dicts, sets, etc.) in the "message" part of failed assertions (as in assert condition, msg) when using -vv: the message now uses the same unlimited repr as the rest of the assertion output, instead of eliding collection elements with ....

• #​12824: Custom command-line options now fail with a clear error when their implicit
  destination conflicts with an existing option, avoiding silent overrides of
  built-in options such as -k.

• #​13292: Fixed a stale rewritten module being used when a test file is modified twice
  within the same second without changing its size -- the pyc header could only
  record whole-second timestamps. The cache is now keyed on a hash of the source.

• #​14036: __tracebackhide__ is now respected in ExceptionGroup tracebacks, both for the group itself and for its sub-exceptions.

• #​14189: Nested usage of caplog.filtering <pytest.LogCaptureFixture.filtering> no longer removes filters early if they were already present.

• #​14412: Fixed incorrect timing information for subtests and parent tests when console_output_style = "times".

• #​14445: Assertion rewriting no longer evaluates walrus operator (:=) expressions more than once, which reported results the test never computed when the expression had side effects.

  An operand evaluated before a later walrus is now reported with the value it actually saw, so assert value != identity(value := value.lower()) keeps Python's left-to-right order.

• [#​14552

[!IMPORTANT]
✂ PR body was truncated to here.